Credential delegation

ABSTRACT

In some implementations, a computing system can be configured so that a first user device can delegate a first user&#39;s media account credentials to second user device corresponding to a second user. For example, a playback device may be configured with the second user&#39;s media account credentials for accessing media items through a network media service. A first user may wish to play media items associated with the first user&#39;s media account credentials on the playback device. To do so, the first user device can request a device identifier for the playback device, request and obtain a delegate token for the device identifier from the media service, and provide the delegate token along with media item information to the playback device. The playback device can then use the delegate token to request the media item associated with the first user&#39;s media access account.

TECHNICAL FIELD

The disclosure generally relates to managing media playback queuesacross computing devices.

BACKGROUND

Many people use their computing device to play and manage media items.For example, a user of a computing device may buy media items (e.g.,music, movies, television shows, etc.) and store the media items on thecomputing device. Often a user will stream a media item from thecomputing device to a playback device, such as a networked speaker,Bluetooth speaker, set-top-box, smart television, etc. However, tocontinue playing the media item on the playback device, the computingdevice must be within range of the playback device so that the computingdevice can continue streaming (e.g., transmitting) the media item to theplayback device.

SUMMARY

In some implementations, a computing device can transfer a playbackqueue between the computing device and a playback device. For example,the computing device can detect when the computing device is within athreshold distance of a playback device. The computing device canestablish a connection to the playback device and receive stateinformation describing the media playback state of the playback device.The computing device can determine the media playback state of thecomputing device. The computing device can present graphical userinterfaces for initiating a transfer of a playback queue between thecomputing device and the playback device based on the playback state ofthe devices. The computing device can initiate a transfer of theplayback queue in response to user input to one of the graphical userinterfaces or automatically based on the context of the computingdevice.

In some implementations, a computing system can be configured so that afirst user device can delegate a first user's media account credentialsto second user device corresponding to a second user. For example, aplayback device may be configured with the second user's media accountcredentials for accessing media items through a network media service. Afirst user may wish to play media items associated with the first user'smedia account credentials on the playback device. To do so, the firstuser device can request a device identifier for the playback device,request and obtain a delegate token for the device identifier from themedia service, and provide the delegate token along with media iteminformation to the playback device. The playback device can then use thedelegate token to request the media item and/or media item keysassociated with the first user's media access account.

Particular implementations provide at least the following advantages. Acomputing device that has sent a media item to a playback device forplayback can be disconnected from a playback device without terminatingplayback of the media item at the playback device. Intuitive graphicaluser interfaces for sending and/or receiving media queues are presentedautomatically and in an intelligent manner based on device playbackstate and/or proximity. By allowing a guest user to delegatecredentials, a guest user can send media items to a playback devicewithout worrying about whether the owner of the playback device hasaccess to the same media item.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an example system for transferring playbackqueues between devices and credential delegation.

FIG. 2 is a flow diagram of an example process for establishing aconnection to a playback device based on proximity.

FIG. 3 is a flow diagram of an example process for sending a playbackqueue to a playback device.

FIG. 4 illustrates an example graphical user interface for transferringplayback of a playback queue from a user device to a playback device.

FIG. 5 is a flow diagram of an example process for retrieving a playbackqueue from a playback device.

FIG. 6 illustrates an example graphical user interface for transferringplayback of a playback queue from a playback device to a user device.

FIG. 7 is a flow diagram of an example process for sending a playbackqueue to a playback device when both user device and playback device areplaying media items.

FIG. 8 is a flow diagram of an example process for retrieving a playbackqueue from a playback device when both a user device and a playbackdevice are currently playing media items.

FIG. 9 illustrates an example graphical user interface for transferringplayback of a playback queue from a user device to a playback device ortransferring playback of a playback queue from a playback device to auser device.

FIG. 10 is a flow diagram of an example process for automaticallytransferring playback of a playback queue from a user device to aplayback device.

FIG. 11 is a device interaction diagram illustrating an example processfor delegating credentials from a first user's device to a second user'sdevice.

FIG. 12 is a block diagram of an example computing device that canimplement the features and processes of FIGS. 1-11.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an example system 100 for transferringplayback queues between devices and credential delegation. For example,system 100 can be configured to transmit playback queues between a userdevice and a playback device so that the receiving device can manageplayback of media items identified in the playback queue. System 100 canbe configured to delegate the media account credentials associated witha first user's device to a second user's device so that the seconduser's device can play back media items associated with the first user'smedia account.

In some implementations, system 100 can include user device 102. Forexample, user device 102 can be a computing device, such as asmartphone, laptop computer, tablet computer, smart watch, or any othercomputing device.

In some implementations, user device 102 can include media application104. For example, media application 104 can be used by the user of userdevice 102 to manage media items (e.g., music tracks, playlists, albums,movies, television shows, radio talk shows, audio books, podcasts, etc.)on user device 102.

In some implementations, media application 104 can be a clientapplication of a network media service. For example, media application104 can be configured with a user's media service account credentialsfor accessing the media service 142 on media server device 140. The usercredentials can include, for example, an account identifier (e.g., username, phone number, device identifier, account token, etc.) and a sharedsecret (e.g., password, encryption key, secret token, fingerprint data,etc.). Media service 142 can provide cloud storage for the user's mediaitems. Media service 142 can provide on demand access to media items,Internet radio, and/or other types of media. A user can interact withvarious graphical user interfaces of media application 104 to accessmedia items through network 150 (e.g., a local area network, wide areanetwork, Wi-Fi network, cellular network, the Internet, etc.). Forexample, the user can generate a playlist of media items. The playlistmay reference media items provided by media service 142. When the userwishes to play back the playlist, media application 104 can load theplaylist into an in-memory playback queue 106. Then media application104 can play the media items in playback queue 106 using the displayand/or speakers of user device 102.

In some implementations, user device 102 can stream a media item to aplayback device. For example, while playing a media item in playbackqueue 106, media application 104 can send the audio and/or videoassociated with the playing media item to playback device 130. Forexample, playback device 130 can be a Wi-Fi speaker, a Bluetoothspeaker, a streaming media device (e.g., set-top-box), a smarttelevision, or any other device capable of receiving and/or presentingaudio and/or video data sent by user device 102. In this instance, mediaapplication 104 is playing back the media item (e.g. received from mediaservice 142), the playback queue being played (e.g., playback queue 106)is still on user device 102, and media application 104 is sending audioand/or video data to playback device 130 for presentation through thespeakers and/or display of playback device 130. If user device 102 ismoved out of range of playback device 130 (e.g., user device 102 losesthe connection to playback device 130), then playback device 120 will nolonger receive the audio and/or video data and playback device 130 willstop playing the audio and/or video associated with the media items inplayback queue 106.

In some implementations, system 100 can include smart playback device120. For example, playback device 120 can be a Wi-Fi speaker, aBluetooth speaker, an in-car entertainment system, a streaming mediadevice (e.g., set-top-box), a smart television, or any other devicecapable of receiving, managing, and playing a playback queue. Like userdevice 102, playback device 120 can be configured with media application122. Media application 122 can have the same, or similar, capabilitiesand/or features as media application 104. For example, media application122 can include playback queue 124 that includes information about mediaitems currently being played by media application 122. In someinstances, playback queue 124 may identify media items provided by mediaservice 142 on media server 140. Playback device 120 can be configuredwith a user's media account credentials for accessing media service 142so that media application 122 can obtain media items identified inplayback queue 124 from media service 142 through network 150.

In some implementations, user device 102 can send playback queue 106 toplayback device 120. For example, user device 102 can receive a wirelesssignal 160 (e.g., Bluetooth, Wi-Fi, etc.) broadcast from playback device120. For example, playback device 120 can periodically broadcast awireless signal so that other devices, such as user device 102, can findand connect to playback device 120. User device 102 can determine, basedon the signal, that user device 102 is within a threshold distance of(e.g., proximate to) playback device 120. In some implementations, inresponse to determining that user device 102 is proximate to playbackdevice 120, user device 102 can present a graphical user interface thata user can interact with to initiate a transfer of playback queue 106and/or playback queue 124 between user device 102 and playback device120, as described in detail below. In some implementations, in responseto determining that user device 102 is proximate to playback device 120and that user device 102 is in a resting position (e.g., on a table,horizontal, not moving, etc.), user device 102 can automaticallyinitiate a transfer of playback queue 106 to playback device 120, asdescribed in detail below.

In some implementations, other criteria (e.g., other than restingposition) can trigger the automatic transfer of a playback queue. Forexample, user device 102 can automatically transfer a playback queueplaying on user device 102 to playback device 120 in response todetecting that user device 102 is proximate to a particular playbackdevice. The user can configure user device 102 to automatically transferplayback of the playback queue playing on user device 102 to theparticular playback device 120 when user device 102 receives the deviceidentifier corresponding to the particular playback device in abroadcast signal and/or when user device 102 is proximate to playbackdevice 120, as described above. For example, the user can configure userdevice 102 to automatically transfer playback of a playback queue toplayback device 120 when user device 102 is proximate to the user'sin-car entertainment system or the user's favorite Bluetooth speaker.

Similarly, user device 102 can automatically transfer a playback queueplaying on user device 102 to playback device 120 in response todetecting that user device 102 is proximate to a particular type ofplayback device. The user can configure user device 102 to automaticallytransfer playback of the playback queue to a type of playback device 120when user device 102 receives a device type identifier corresponding tothe particular type of playback device in a broadcast signal and/or whenuser device 102 is proximate to playback device 120, as described above.For example, the user can configure user device 102 to automaticallytransfer playback of a playback queue to playback device 120 when userdevice 102 is playing media items in the playback queue and user device102 proximate to any in-car entertainment system.

In some implementations, user device 102 can automatically transfer aplayback queue playing on user device 102 to playback device 120 inresponse to detecting that user device 102 is next to playback device102. For example, user device 102 can be configured with a proximitythreshold distance, as described above. User device 102 can beconfigured with a second threshold distance that is less than theproximity threshold distance. The second threshold distance can be usedto determine when user device 102 is next to playback device 102. Forexample, the second threshold distance can be 6 inches. When user device102 is playing media items in playback queue, user device 102 canautomatically transfer playback of the playback queue when user device102 determines that user device is within 6 inches of playback device120.

FIG. 2 is a flow diagram of an example process 200 for establishing aconnection to a playback device based on proximity. For example, userdevice 102 can perform the steps of process 200 to detect and connect toplayback device 120.

At step 202, user device 102 can scan for wireless broadcasts. Forexample, user device 102 can scan for wireless signals broadcast fromother devices, such as other computers, accessories, speakers, playbackdevice 120, etc. For example, playback device 120 can broadcast thesignal using Bluetooth, Bluetooth LE, peer-to-peer Wi-Fi, near fieldcommunication (NFC), ultra-wideband or other wireless broadcastingtechnologies. Playback device 120 can broadcast the signal as anadvertisement of availability or to indicate a service that they canprovide. Playback device 120 can include a device identifier for theplayback device 120 in the broadcast signal. For example, the deviceidentifier can be a Bluetooth MAC (media access control) address, avirtual MAC address, or some other identifier associated with thebroadcasting device. Playback device 120 can broadcast the signalperiodically (e.g., every second, every 10 seconds, etc.).

In some implementations, user device 102 can scan periodically for thewireless broadcasts. In some implementations, user device 102 can scanfor the wireless broadcasts in response to some event at user device102. For example, the event can correspond to the user providing inputto user device 102, user device 102 waking from a low power state, thedisplay of user device 102 being illuminated, user device 102 turning onone or more communication radios within user device 102, user device 102detecting some movement of user device 102, or some other event.

At step 204, user device 102 can receive a wireless broadcast signalfrom playback device 120. For example, while scanning for wirelesssignals, user device 102 can receive a wireless signal broadcast fromplayback device 120. The received signal can include a device identifierfor playback device 120. User device 120 can determine the receivedsignal strength indicator for the received signal according towell-known processes. User device 120 can determine the time of flightof the signal according to well-known processes.

At step 206, user device 102 can determine the distance to playbackdevice 120. For example, user device 102 can determine the distancebetween user device 102 and playback device 120 based on the determinedreceived signal strength indicator and/or determined time of flight forthe received signal, according to well-known processes.

At step 208, user device 102 can determine that user device 102 iswithin a threshold distance of playback device 120. For example, userdevice 102 can be configured with a threshold distance for determiningwhether user device 102 is proximate (e.g., close, nearby, etc.) anotherdevice (e.g., playback device 120). User device 102 can compare thedistance determined at step 206 to the threshold distance to determinewhether the determined distance is less than the threshold distance.When the threshold distance is less than the threshold distance, userdevice 102 can determine that user device 102 is proximate to playbackdevice 120 and continue process 200 to establish a connection withplayback device 120. When the threshold distance is greater than orequal to the threshold distance, user device 102 can determine that userdevice 102 is not proximate to playback device 120 terminate process 200at step 208.

At step 210, user device 102 can obtain the device identifier forplayback device 120 from the wireless signal. As described above, thewireless signal received by user device 102 can include the deviceidentifier for the broadcasting device (e.g., playback device 120). Userdevice 102 can obtain the device identifier for playback device 120 fromthe received wireless signal.

At step 212, user device 102 can scan the local network for the deviceidentifier corresponding to playback device 120. For example, the localnetwork can be a Wi-Fi network, local area network, etc. Devicesconnected to the local network can broadcast their availability on thenetwork by sending advertising messages that include the deviceidentifier of the broadcasting device. For example, playback device 120can send an advertising message over the local network that includes thedevice identifier of playback device 120 and/or information (e.g., IPaddress, device name, MAC address, etc.) needed to connect to playbackdevice 120 over the local network. The device identifier broadcast onthe local network can be the same device identifier broadcast in thewireless signal described above. User device 102 can receive the localnetwork advertisement messages and compare the device identifier in thewireless broadcast to the advertisement messages received on the localnetwork to find the advertisement message broadcast by playback device120. Alternatively, when an internet protocol (IP) address (e.g., deviceidentifier) for the broadcasting playback device 120 is included in thewireless signal broadcast received at step 204, user device 102 can skipstep 212 and connect to playback device 120 using the IP address fromthe wireless signal.

At step 214, user device 120 can establish a network connection toplayback device 120 based on the device identifier. For example, userdevice 120 can use the information in the local network advertisementmessage to establish a connection over the local network to playbackdevice 120. In some implementations, user device 102 can establish apoint-to-point Wi-Fi connection (e.g., AWDL) with playback device 120 ifplayback device 120 is not on the same network as user device 102. Insome implementations, user device 102 can use an IP address included inthe wireless signal to establish a connection to playback device 120.

While process 200 describes playback device 120 as the broadcastingdevice and user device 102 as the scanning device for establishing theconnection between playback device 120 and user device 102, the roles ofplayback device 120 and user device 102 in process 200 can be reversed.For example, user device 102 can broadcast a wireless signal indicatingthat user device 102 is available to connect to a playback device. Userdevice 102 can, for example, broadcast the signal upon waking, uponreceiving some user input, upon detecting movement, etc. Playback device120 can periodically scan for broadcast signals and when a signal isreceived from user device 102, playback device 120 can determineproximity and establish a local network connection to user device 102using the mechanisms above in process 200.

As described above, process 200 assumes that a relationship between userdevice 102 and playback device 120 has already been established. Forexample, prior to performing process 200, user device 102 and playbackdevice 120 may need to be setup so that user device 102 is authorized toaccess playback device 120 without additional user input to performauthentication and/or authorization of user device 102. Thisrelationship can be setup using well known device pairing techniquesand/or as described with reference to U.S. patent application Ser. No.13/913,172, which is incorporated herein by reference.

FIG. 3 is a flow diagram of an example process 300 for sending aplayback queue to a playback device. For example, process 300 can beperformed by user device 102 after establishing a connection withplayback device 120 according to process 200 described above.

At step 302, user device 102 can obtain the playback state of playbackdevice 120. For example, media application 104 can send a message tomedia application 122 on playback device 120 requesting the playbackstate of media application 122. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is not playing anymedia items at the time of the request. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is currently playinga media item.

At step 304, user device 102 can obtain the playback state of userdevice 102. For example, media application 104 can obtain informationindicating whether media application 104 is currently playing any mediaitem.

At step 306, user device 102 can determine that user device 102 iscurrently playing a media item. For example, media application 104 candetermine that media application 104 is currently playing a media itembased on the state information obtained at step 304.

At step 308, user device 102 can determine that playback device 120 isnot currently playing a media item. For example, media application 104can determine that media application 122 is not currently playing amedia item based on the state information obtained at step 302.

At step 310, user device 102 can present a graphical user interface forsending the playback queue of user device 102 to playback device 120.For example, based on the determination that media application 104 onuser device 102 is currently playing a media item and that mediaapplication 122 on playback device 120 is not currently playing a mediaitem, user device 102 can present a graphical user interface (e.g.,graphical user interface 400 of FIG. 4) that a user can manipulate tocause media application 104 to transfer playback of playback queue 106to playback device 120. In this case, transferring playback queue 106 toplayback device 120 will cause media application 122 on playback device120 take over playback of playback queue 106 from media application 104.

FIG. 4 illustrates an example graphical user interface 400 fortransferring playback of playback queue 106 from user device 102 toplayback device 120. For example, graphical user interface (GUI) 400 canbe presented when user device 120 determines that media application 104on user device 102 is playing a media item and media application 122 onplayback device 120 is not playing a media item. In someimplementations, GUI 400 can be presented on a lock screen of userdevice 102. Thus, a user may manipulate GUI 400 when user device islocked and without unlocking user device 102 (e.g., before entering theuser's credentials to unlock user device 102).

In some implementations, GUI 400 can include graphical element 402. Forexample, graphical element 402 can include a prompt informing the userthat manipulation of graphical element 402 will cause user device 102 tosend playback of playback queue 106 to the detected proximate playbackdevice (e.g., playback device 120). The user may provide input (e.g.,touch input) to move or manipulate graphical element 402 on GUI 400. Forexample, the user may provide input in the form of a swipe gesture(e.g., touch and drag) in an upward motion (e.g., away from the user) onthe display of user device 102 to initiate the transfer of playbackbetween devices.

Returning to FIG. 3, at step 312, user device 102 can receive user inputfor sending playback queue 106 to playback device 120. For example,media application 104 can receiving user input manipulating graphicalelement 402.

At step 314, user device 102 can stop playback of playback queue 106.For example, media application 104 can stop playback of the currentlyplaying media item and record the location (e.g., time offset) in themedia item where playback was stopped. The time offset can be stored inthe corresponding media item data in playback queue 106. In someimplementations, media application 104 can store an indication of whichmedia item was playing when playback of playback queue 106 was stopped.For example, media application 104 can store the media item identifierfor the stopped or interrupted media item in playback queue 106.

At step 316, user device 102 can send playback queue 106 to playbackdevice 120. For example, media application 104 can send playback queue106 to media application 122 on playback device 120. Playback queue 106can include an ordered collection of media items. Each media item in theplayback queue can include media item data, including a media itemidentifier (e.g., track identifier, movie identifier, television episodeidentifier, etc.), an account identifier that identifies the account ofthe user who enqueued the media item, and/or a delegate token (describedfurther below). For the interrupted media item (e.g., the first mediaitem in the queue), the media item data can include a time offset thatindicates the current position of playback. When sending playback queue106 at step 316, media application 104 can include an indication thatmedia application 122 should take over playback of playback queue 106.When sending playback queue 106 at step 316, media application 104 caninclude an indication (e.g., a media item identifier) of which mediaitem was stopped or interrupted when playback of playback queue 106 wasstopped so that media application 122 can resume play back at theindicated media item. When media application 122 receives playback queue106, media application 122 can save playback queue 106 as playback queue124 and continue playback of playback queue 124 (e.g., playback queue106) at the time offset indicated in the media item in playback queue124 that media application 104 indicated should be resumed. Thus, a usercan cause user device 102 to transfer playback of a playback queuecurrently being played by user device 102 to a nearby playback device.

FIG. 5 is a flow diagram of an example process 500 for retrieving aplayback queue from a playback device. For example, process 500 can beperformed by user device 102 after establishing a connection withplayback device 120 according to process 200 described above.

At step 502, user device 102 can obtain the playback state of playbackdevice 120. For example, media application 104 can send a message tomedia application 122 on playback device 120 requesting the playbackstate of media application 122. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is not playing anymedia items at the time of the request. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is currently playinga media item.

At step 504, user device 102 can obtain the playback state of userdevice 102. For example, media application 104 can obtain informationindicating whether media application 104 is currently playing any mediaitem.

At step 506, user device 102 can determine that user device 102 is notcurrently playing a media item. For example, media application 104 candetermine that media application 104 is not currently playing a mediaitem based on the state information obtained at step 504.

At step 508, user device 102 can determine that playback device 120 iscurrently playing a media item. For example, media application 104 candetermine that media application 122 is currently playing a media itembased on the state information obtained at step 502.

At step 510, user device 102 can present a graphical user interface forrequesting the playback queue from playback device 120. For example,based on the determination that media application 104 on user device 102is not currently playing a media item and that media application 122 onplayback device 120 is currently playing a media item, user device 102can present a graphical user interface (e.g., graphical user interface600 of FIG. 6) that a user can manipulate to cause media application 104to transfer playback of playback queue 124 from playback device 120 touser device 102. In this case, transferring playback queue 124 toplayback device 102 will cause media application 104 on user device 102to take over playback of playback queue 124 from media application 122.

FIG. 6 illustrates an example graphical user interface 600 fortransferring playback of playback queue 124 from playback device 120 touser device 102. For example, graphical user interface (GUI) 400 can bepresented when user device 120 determines that media application 104 onuser device 102 is not playing a media item and media application 122 onplayback device 120 is playing a media item. In some implementations,GUI 600 can be presented on a lock screen of user device 102. Thus, auser may manipulate GUI 400 when user device is locked and withoutunlocking user device 102 (e.g., before entering the user's credentialsto unlock user device 102).

In some implementations, GUI 600 can include graphical element 602. Forexample, graphical element 602 can include a prompt informing the userthat manipulation of graphical element 602 will cause user device 102 totransfer playback of playback queue 124 on the detected proximateplayback device (e.g., playback device 120) to user device 102. The usermay provide input (e.g., touch input) to move or manipulate graphicalelement 602 on GUI 600. For example, the user may provide input in theform of a swipe gesture (e.g., touch and drag) in an downward motion(e.g., toward from the user) on the display of user device 102 toinitiate the transfer of playback between devices.

Returning to FIG. 5, at step 512, user device 102 can receive user inputfor transferring playback of playback queue 124 to user device 102. Forexample, media application 104 can receive user input manipulatinggraphical element 602, described above.

At step 514, user device 102 can send a request to take over playback ofplayback queue 124 to playback device 120. For example, in response toreceiving the user input at step 512, media application 104 can send amessage to media application 122 on playback device 120 requesting thatplayback of playback queue 124 be transferred to media application 104on user device 102. In response to receiving the request, mediaapplication 122 on playback device 120 can stop playback of thecurrently playing media item in playback queue 124 and record thelocation (e.g., time offset) where playback was stopped in the mediaitem. The time offset can be stored in the corresponding media item data(e.g., in the first media item) in playback queue 124. In someimplementations, media application 122 can store an indication of whichmedia item was playing when playback of playback queue 124 was stopped.For example, media application 122 can store the media item identifierfor the stopped or interrupted media item in playback queue 124.

At step 516, user device 102 can receive playback queue 124 fromplayback device 120. For example, media application 122 can sendplayback queue 124 to media application 104 on user device 102. Playbackqueue 124 can include an ordered collection of media items. Each mediaitem in the playback queue can include media item data, including amedia item identifier (e.g., track identifier, movie identifier,television episode identifier, etc.), an account identifier thatidentifies the account of the user who enqueued the media item, and/or adelegate token (described further below). For the interrupted media item(e.g., the first media item in the queue), the media item data caninclude a time offset that indicates the current position of playback.When sending playback queue 124 at step 516, media application 122 caninclude an indication that media application 104 should take overplayback of playback queue 124. When sending playback queue 124 at step516, media application 122 can include an indication (e.g., theidentifier for the interrupted media item) of which media item inplayback queue 124 should be played first so that media application 122can resume play back at the indicated media item. When media application104 receives playback queue 124, media application 104 can save playbackqueue 124 as playback queue 106.

At step 518, user device 102 can initiate playback of playback queue 106on user device 102. For example, media application 104 can continueplayback of playback queue 106 (e.g., playback queue 124) at the timeoffset indicated in the media item in playback queue 106 that mediaapplication 122 indicated should be resumed. Thus, a user can cause userdevice 102 to transfer playback of a playback queue currently beingplayed by a nearby playback device to user device 102.

FIG. 7 is a flow diagram of an example process 700 for sending aplayback queue to a playback device when both user device and playbackdevice are playing media items. For example, process 700 can beperformed by user device 102 after establishing a connection withplayback device 120 according to process 200 described above.

At step 702, user device 102 can obtain the playback state of playbackdevice 120. For example, media application 104 can send a message tomedia application 122 on playback device 120 requesting the playbackstate of media application 122. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is not playing anymedia items at the time of the request. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is currently playinga media item.

At step 704, user device 102 can obtain the playback state of userdevice 102. For example, media application 104 can obtain informationindicating whether media application 104 is currently playing any mediaitem.

At step 706, user device 102 can determine that user device 102 iscurrently playing a media item. For example, media application 104 candetermine that media application 104 is currently playing a media itembased on the state information obtained at step 304.

At step 708, user device 102 can determine that playback device 120 iscurrently playing a media item. For example, media application 104 candetermine that media application 122 is currently playing a media itembased on the state information obtained at step 302.

At step 710, user device 102 can present a graphical user interface forsending the playback queue of user device 102 to playback device 120 orrequesting the playback queue of playback device 120. For example, basedon the determination that media application 104 on user device 102 iscurrently playing a media item and that media application 122 onplayback device 120 is also currently playing a media item, user device102 can present a graphical user interface (e.g., graphical userinterface 900 of FIG. 9) that a user can manipulate to cause mediaapplication 104 to transfer playback of playback queue 106 to playbackdevice 120 or transfer playback of playback queue 124 to user device102. In this case, transferring playback queue 106 to playback device120 will cause media application 122 on playback device 120 take overplayback of playback queue 106 from media application 104, as describedabove with reference to process 300 of FIG. 3. Similarly, transferringplayback queue 124 to user device 102 will cause media application 104on user device 102 take over playback of playback queue 124 from mediaapplication 122, as described above with reference to process 500 ofFIG. 5.

FIG. 9 illustrates an example graphical user interface 900 fortransferring playback of playback queue 106 from user device 102 toplayback device 120 or transferring playback of playback queue 124 fromplayback device 120 to user device 102. For example, graphical userinterface (GUI) 900 can be presented when user device 120 determinesthat media application 104 on user device 102 is playing a media itemand media application 122 on playback device 120 is also playing a mediaitem. In some implementations, GUI 900 can be presented on a lock screenof user device 102. Thus, a user may manipulate GUI 900 when user deviceis locked and without unlocking user device 102 (e.g., before enteringthe user's credentials to unlock user device 102).

In some implementations, GUI 900 can include graphical element 902. Forexample, graphical element 902 can include a prompt informing the userthat manipulation of graphical element 902 will cause user device 102 tosend playback of playback queue 106 to the detected proximate playbackdevice (e.g., playback device 120). The user may provide input (e.g.,touch input) to move or manipulate graphical element 902 on GUI 900. Forexample, the user may provide input in the form of a swipe gesture(e.g., touch and drag) in an upward motion (e.g., away from the user) onthe display of user device 102 to initiate the transfer of playback fromuser device 102 to playback device 120.

In some implementations, GUI 900 can include graphical element 904. Forexample, graphical element 904 can include a prompt informing the userthat manipulation of graphical element 904 will cause user device 102 totransfer playback of playback queue 124 on the detected proximateplayback device (e.g., playback device 120) to user device 102. The usermay provide input (e.g., touch input) to move or manipulate graphicalelement 904 on GUI 900. For example, the user may provide input in theform of a swipe gesture (e.g., touch and drag) in a downward motion(e.g., toward the user) on the display of user device 102 to initiatethe transfer of playback from playback device 120 to user device 102.

Returning to FIG. 7, at step 712, user device 102 can receive user inputfor sending playback queue 106 to playback device 120. For example,media application 104 can receiving user input manipulating graphicalelement 902.

At step 714, user device 102 can stop playback of playback queue 106.For example, media application 104 can stop playback of the currentlyplaying media item and record the location (e.g., time offset) in themedia item where playback was stopped. The time offset can be stored inthe corresponding media item data in playback queue 106. In someimplementations, media application 104 can store an indication of whichmedia item was playing when playback of playback queue 106 was stopped.For example, media application 104 can store the media item identifierfor the stopped or interrupted media item in playback queue 106.

At step 316, user device 102 can send playback queue 106 to playbackdevice 120. For example, media application 104 can send playback queue106 to media application 122 on playback device 120. Playback queue 106can include an ordered collection of media items. Each media item in theplayback queue can include media item data, including a media itemidentifier (e.g., track identifier, movie identifier, television episodeidentifier, etc.), an account identifier that identifies the account ofthe user who enqueued the media item, and/or a delegate token (describedfurther below). For the interrupted media item (e.g., the first mediaitem in the queue), the media item data can include a time offset thatindicates the current position of playback. When sending playback queue106 at step 316, media application 104 can include an indication thatmedia application 122 should take over playback of playback queue 106.When sending playback queue 106 at step 316, media application 104 caninclude an indication (e.g., a media item identifier) of which mediaitem was stopped or interrupted when playback of playback queue 106 wasstopped so that media application 122 can resume play back at theindicated media item. When media application 122 receives playback queue106, media application 122 can save playback queue 106 as playback queue124 and continue playback of playback queue 124 (e.g., playback queue106) at the time offset indicated in the media item in playback queue124 that media application 104 indicated should be resumed. Thus, a usercan cause user device 102 to transfer playback of a playback queuecurrently being played by user device 102 to a nearby playback device.

FIG. 8 is a flow diagram of an example process 800 for retrieving aplayback queue from a playback device when both user device 102 andplayback device 120 are currently playing media items. For example,process 800 can be performed by user device 102 after establishing aconnection with playback device 120 according to process 200 describedabove.

At step 802, user device 102 can obtain the playback state of playbackdevice 120. For example, media application 104 can send a message tomedia application 122 on playback device 120 requesting the playbackstate of media application 122. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is not playing anymedia items at the time of the request. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is currently playinga media item.

At step 804, user device 102 can obtain the playback state of userdevice 102. For example, media application 104 can obtain informationindicating whether media application 104 is currently playing any mediaitem.

At step 806, user device 102 can determine that user device 102 is notcurrently playing a media item. For example, media application 104 candetermine that media application 104 is not currently playing a mediaitem based on the state information obtained at step 804.

At step 808, user device 102 can determine that playback device 120 iscurrently playing a media item. For example, media application 104 candetermine that media application 122 is currently playing a media itembased on the state information obtained at step 802.

At step 810, user device 102 can present a graphical user interface forrequesting the playback queue from playback device 120. For example,based on the determination that media application 104 on user device 102is not currently playing a media item and that media application 122 onplayback device 120 is currently playing a media item, user device 102can present a graphical user interface (e.g., graphical user interface900 of FIG. 9) that a user can manipulate to cause media application 104to transfer playback of playback queue 124 from playback device 120 touser device 102. In this case, transferring playback queue 124 toplayback device 102 will cause media application 104 on user device 102take over playback of playback queue 124 from media application 122.

FIG. 9 illustrates an example graphical user interface 900 fortransferring playback of playback queue 106 from user device 102 toplayback device 120 or transferring playback of playback queue 124 fromplayback device 120 to user device 102. For example, graphical userinterface (GUI) 900 can be presented when user device 120 determinesthat media application 104 on user device 102 is playing a media itemand media application 122 on playback device 120 is also playing a mediaitem. In some implementations, GUI 900 can be presented on a lock screenof user device 102. Thus, a user may manipulate GUI 900 when user deviceis locked and without unlocking user device 102 (e.g., before enteringthe user's credentials to unlock user device 102).

In some implementations, GUI 900 can include graphical element 902. Forexample, graphical element 902 can include a prompt informing the userthat manipulation of graphical element 902 will cause user device 102 tosend playback of playback queue 106 to the detected proximate playbackdevice (e.g., playback device 120). The user may provide input (e.g.,touch input) to move or manipulate graphical element 902 on GUI 00. Forexample, the user may provide input in the form of a swipe gesture(e.g., touch and drag) in an upward motion (e.g., away from the user) onthe display of user device 102 to initiate the transfer of playback fromuser device 102 to playback device 120.

In some implementations, GUI 900 can include graphical element 904. Forexample, graphical element 904 can include a prompt informing the userthat manipulation of graphical element 904 will cause user device 102 totransfer playback of playback queue 124 on the detected proximateplayback device (e.g., playback device 120) to user device 102. The usermay provide input (e.g., touch input) to move or manipulate graphicalelement 904 on GUI 900. For example, the user may provide input in theform of a swipe gesture (e.g., touch and drag) in an downward motion(e.g., toward from the user) on the display of user device 102 toinitiate the transfer of playback from playback device 120 to userdevice 102.

Returning to FIG. 8, at step 812, user device 102 can receive user inputfor transferring playback of playback queue 124 to user device 102. Forexample, media application 104 can receive user input manipulatinggraphical element 904, described above.

At step 914, user device 102 can send a request to take over playback ofplayback queue 124 to playback device 120. For example, in response toreceiving the user input at step 912, media application 104 can send amessage to media application 122 on playback device 120 requesting thatplayback of playback queue 124 be transferred to media application 104on user device 102. In response to receiving the request, mediaapplication 122 on playback device 120 can stop playback of thecurrently playing media item in playback queue 124 and record thelocation (e.g., time offset) where playback was stopped in the mediaitem. The time offset can be stored in the corresponding media item data(e.g., in the first media item) in playback queue 124. In someimplementations, media application 122 can store an indication of whichmedia item was playing when playback of playback queue 124 was stopped.For example, media application 122 can store the media item identifierfor the stopped or interrupted media item in playback queue 124.

At step 916, user device 102 can receive playback queue 124 fromplayback device 120. For example, media application 122 can sendplayback queue 124 to media application 104 on user device 102. Playbackqueue 124 can include an ordered collection of media items. Each mediaitem in the playback queue can include media item data, including amedia item identifier (e.g., track identifier, movie identifier,television episode identifier, etc.), an account identifier thatidentifies the account of the user who enqueued the media item, and/or adelegate token (described further below). For the interrupted media item(e.g., the first media item in the queue), the media item data caninclude a time offset that indicates the current position of playback.When sending playback queue 124 at step 916, media application 122 caninclude an indication that media application 104 should take overplayback of playback queue 124. When sending playback queue 124 at step916, media application 122 can include an indication (e.g., theidentifier for the interrupted media item) of which media item inplayback queue 124 should be played first so that media application 122can resume play back at the indicated media item. When media application104 receives playback queue 124, media application 104 can save playbackqueue 124 as playback queue 106.

At step 918, user device 102 can initiate playback of playback queue 106on user device 102. For example, media application 104 can continueplayback of playback queue 106 (e.g., playback queue 124) at the timeoffset indicated in the media item in playback queue 106 that mediaapplication 122 indicated should be resumed. Thus, a user can cause userdevice 102 to transfer playback of a playback queue currently beingplayed by a nearby playback device to user device 102.

FIG. 10 is a flow diagram of an example process 1000 for automaticallytransferring playback of a playback queue from a user device to aplayback device. For example, process 1000 can be performed by userdevice 102 to automatically transfer playback of a playback queue to aplayback device when user device 102 is playing media items from aplayback queue and user device 102 detects that user device 102 has beenplaced in a resting position near the playback device.

At step 1002, user device 102 can obtain the playback state of playbackdevice 120. For example, media application 104 can send a message tomedia application 122 on playback device 120 requesting the playbackstate of media application 122. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is not playing anymedia items at the time of the request. Media application 122 can send aresponse to media application 104 indicating that the playback state ofmedia application 122 is that media application 122 is currently playinga media item.

At step 1004, user device 102 can obtain the playback state of userdevice 102. For example, media application 104 can obtain informationindicating whether media application 104 is currently playing any mediaitem.

At step 1006, user device 102 can determine that user device 102 iscurrently playing a media item. For example, media application 104 candetermine that media application 104 is currently playing a media itembased on the state information obtained at step 304.

At step 1008, user device 102 can determine that playback device 120 isnot currently playing a media item. For example, media application 104can determine that media application 122 is not currently playing amedia item based on the state information obtained at step 302.

At step 1010, user device 102 can determine that user device 102 is in aresting position. For example, user device 102 can include motionsensors to detect the position, orientation, and/or movement of userdevice 102. When a user places user device 102 in a resting position(e.g., motionless, on a table, horizontally oriented, etc.), user device102 can receive motion data from the motion sensors and determine thatuser device 102 has been placed in the resting position.

At step 1012, user device 102 can automatically send playback queue 106to playback device 120. For example, in response to determining thatuser device 102 is proximate to playback device 102, that user device102 is currently playing a playback queue and playback device 102 isnot, and/or that user device 102 is in a resting position, mediaapplication 104 on user device 102 can automatically transfer playbackof playback queue 106 to media application 122 on playback device 120.For example, media application 104 can stop playback of the currentlyplaying media item and record the location (e.g., time offset) in themedia item where playback was stopped. The time offset can be stored inthe corresponding media item data in playback queue 106. In someimplementations, media application 104 can store an indication of whichmedia item was playing when playback of playback queue 106 was stopped.For example, media application 104 can store the media item identifierfor the stopped or interrupted media item in playback queue 106.

After stopping playback of playback queue 106, media application 104 cansend playback queue 106 to media application 122 on playback device 120.Playback queue 106 can include an ordered collection of media items.Each media item in the playback queue can include media item data,including a media item identifier (e.g., track identifier, movieidentifier, television episode identifier, etc.), an account identifierthat identifies the account of the user who enqueued the media item,and/or a delegate token (described further below). For the interruptedmedia item (e.g., the first media item in the queue), the media itemdata can include a time offset that indicates the current position ofplayback. When sending playback queue 106 at step 1012, mediaapplication 104 can include an indication that media application 122should take over playback of playback queue 106. When sending playbackqueue 106 at step 1012, media application 104 can include an indication(e.g., a media item identifier) of which media item was stopped orinterrupted when playback of playback queue 106 was stopped so thatmedia application 122 can resume play back at the indicated media item.When media application 122 receives playback queue 106, mediaapplication 122 can save playback queue 106 as playback queue 124 andcontinue playback of playback queue 124 (e.g., playback queue 106) atthe time offset indicated in the media item in playback queue 124 thatmedia application 104 indicated should be resumed. Thus, user device 102can automatically transfer playback of a playback queue currently beingplayed by user device 102 to a nearby playback device.

The playback queue transfer processes described above describe a processthat stops play back at a playback sending device (e.g., user device 102or playback device 120), transfers the playback queue, and starts playback at a playback receiving device (e.g., playback device 120 or userdevice 102) at a location in a media item where playback was stopped. Insome implementations, transferring playback (e.g., a playback queue)between a playback sending device and a playback receiving device can beperformed without interrupting playback. For example, the playback queueon the sending device can be send to the receiving device while thesending device continues to play media items in the playback queue. Thereceiving device can synchronize playback of media items in the playbackqueue on the receiving device such that both receiving device andsending device are playing the same media item in the playback queue inharmony. After playback has begun on the receiving device, the sendingdevice can fade out (e.g., reduce the volume) of the playing media itemon the sending device and finally stop playback on the sending device.Thus, the transfer of playback of the playback queue can be performedwithout interrupting the playback of the media items in the playbackqueue.

In some implementations, playback of a playback queue can be movedbetween playback devices. For example, multiple playback devices 120 canbe configured to play media items together. A primary playback device120 can manage playback queue 124 and send audio and/or video data tosecondary playback devices 120. To provide failover should the primaryplayback device 120 fail (e.g., lose power, lose network connection,shutdown, etc.), the primary playback device 120 and secondary playbackdevices 120 can synchronize playback queues. When a secondary playbackdevice 120 determines that the primary playback device 120 is no longerreachable, the secondary playback device 120 can take over as theprimary playback device 120 can take over management of the playbackqueue, including coordinating play back among the remaining secondaryplayback devices 120.

FIG. 11 is a device interaction diagram illustrating an example process1100 for delegating credentials from a first user's device to a seconduser's device. For example, typically user device 102 and playbackdevice 120 will be owned by the same user and configured with the sameuser account credentials for accessing media service 142 and obtainingmedia items from media service 142. However, in some instances, userdevice 102 may be owned by a different user than playback device 120and/or configured with different user account credentials than userdevice 102. If user device 102 sends a playback queue to playback device120 that includes a media item that the user of playback back device 120does not have access to, playback device 120 may not be able to play themedia item. Process 1100 provides for delegating the user credentials ofuser device 102 to playback device 120 so that playback device 120 canplay media items that playback device 120 may not have access tootherwise.

In some implementations, process 1100 can be performed after user device102 establishes a connection to playback device 120, as described abovewith reference to process 200 of FIG. 2. In some implementations,process 110 can be performed after user device 102 connects to playbackdevice 120 through other means (e.g., Bluetooth pairing, other Wi-Fidiscovery mechanisms, etc.). For example, when user device 102 connectsto the same local network as playback device 120, user device 102 can benotified of the availability of playback device 120. Media application104 can present an graphical user interface that allows the user of userdevice 102 to connect to playback device 120 through the local network.The user can provide input selecting the playback device 120 and userdevice 102 can connect to playback device 120 through the local network.

In some implementations, playback device 120 can be configured toprovide access control to playback device 120. For example, a user canconfigure playback device 120 so that other users can only connect toplayback device 120 under certain conditions. For example, playbackdevice 120 can be configured with a password. When user device 102provides the password to playback device 120 (e.g., after the userinputs the password), then playback device 120 can allow user device 120to connect to playback device 120 and modify playback queue 124. If userdevice 102 has access to a network managed home environment and playbackdevice 120 is part of the home environment, then playback device 120 canallow user device 102 to connect to playback device 120 and modifyplayback queue 124. Playback device 120 can be configured to allow userdevice to access playback device 120 when user device 102 is in the samelocation (e.g., same home, geofence, etc.) as playback device 120, orconnected to the same local network as playback device 120. In someimplementations, playback device 120 can be configured to allow anydevice to access playback device 120. In some implementations, playbackdevice 120 can require user device 120 to provide a password in additionto or instead of any of the criteria described above.

At operation 1102, user device 102 can request a device identifier fromplayback device 120. For example, media application 104 can request thedevice identifier from playback device 120 (e.g., media application 122)so that user device 102 can later obtain a delegate token for playbackdevice 120.

At operation 1104, playback device 120 can send the device identifierfor playback device 120 to user device 102. For example, the deviceidentifier can be an identifier for playback device 120 that has beenregistered with or used to access media service 142 on media server 140.The device identifier can be an identifier assigned to playback device120 by the user/owner of playback device 120. The device identifier canbe a hardware identifier associated with playback device 120 assigned atthe factory where playback device 120 was made. The device identifiercan be a media access control (MAC) address or a virtual identifierassigned to playback device 120.

At operation 1106, user device 102 can request a delegate token forplayback device 120. For example, in response to receiving the deviceidentifier for playback device 120 at operation 1104, media application104 can send a message to media service 142 on media server 140requesting a delegate token for playback device 120. For example, themessage (e.g., the delegate token request) can include the deviceidentifier for playback device 120 and/or the media service accountcredentials (e.g., user name, password, etc.) of the user of user device102. If music application 104 has already logged in and/or established aconnection to media service 142, music application 104 can send thedevice identifier in the delegate token request without the user's mediaaccount credentials.

At operation 1108, media server 140 can generate a delegate tokenassociated with the device identifier of playback device 120. Forexample, the delegate token can be randomly generated data. Mediaservice 142 can store the delegate token in the media service account ofthe user of user device 102 and in association with (e.g., mapped to)the device identifier of playback device. Alternatively, the delegatetoken can be generated based on or derived from the device identifierand/or the media service account identifier of the user of user device102. For example, media service 142 can sign token data, including thedevice identifier, media service account identifier, and some randomanti-replay data, with a private key corresponding to media service 142.120.

At operation 1110, media server 140 can send the delegate token to userdevice 102. For example, media service 142 can send the delegate tokenstored in association with the device identifier of playback device 120to user device 102.

At operation 1112, user device 102 can send a playback queue, includingthe delegate token for playback device 120, to playback device 120. Forexample, the playback queue (e.g., playback queue 106) can include oneor more media items to be added to the playback queue (e.g., playbackqueue 124) of media application 122 on playback device 120. As describedabove, each media item in playback queue 106 can include a media itemidentifier (e.g., a URL for obtaining the media item asset), an accountidentifier for the media service account configured on user device 102(e.g., the account enqueuing the media item), and the delegate tokenassociated with the account identifier and the device identifier ofplayback device 120 (e.g., generated at operation 1108).

At operation 1114, playback device 120 can request a media asset frommedia server 140 using the delegate token. For example, when mediaapplication 122 on playback device 120 selects a media item in playbackqueue 124 for play back and determines that the account identifier forthe media item in the queue does not correspond to the media serviceaccount identifier configured for playback device 120, playback devicecan send a message requesting access to the media item through the mediaservice account associated with the media item in the playback queue.For example, the message can include the device identifier for playbackdevice 120, the media item identifier for the selected media item, mediaservice account identifier for the selected media item, and delegatetoken for the selected media item.

At operation 1116, media server 140 can validate the delegate token. Forexample, media service 142 can receive the device identifier forplayback device 120, the media item identifier, media service accountidentifier, and delegate token for the selected media item in themessage sent at operation 1114. Media service 140 can obtain the accountinformation associated with the media service account identifier. Theaccount information can include a mapping of playback device identifiersto delegate tokens stored at media service 142. Media service 140 canuse the device identifier for playback device 120 to obtain thecorresponding stored delegate token for playback device 120. Mediaservice 140 can compare the obtained stored delegate token for playbackdevice 120 to the delegate token receive from playback device 120 in themessage of operation 1114. If the tokens match (e.g., the tokens are thesame), then media service 142 can determine that the received delegatetoken is valid.

Alternatively, when the delegate token includes the signed token data(e.g., device identifier, account identifier, and/or anti-replay data),as described above, media service 142 can attempt to verify thesignature on the received delegate token to determine whether the tokenwas generated by media service 142. If the token was not signed usingthe private key of media service 142, then media service 142 candetermine that the delegate token is not valid. If the token was signedby media service 142, then media service 142 can determine whether theplayback device that sent the delegate token corresponds to the deviceidentifier included in the token data. If media service 142 can verifythe signature on the delegate token and can confirm that the deviceidentifier corresponds to the playback device, then media service 142can determine that the delegate token is valid.

At operation 1118, media server 140 can send the requested media assetand/or media keys to playback device 120. For example, media service 142can send (e.g., stream) the audio and/or video data (e.g., the mediaasset) corresponding requested media item to media application 122 onplayback device 120. In this case, the media asset is provided throughthe media service account of the user of user device 102 even thoughplayback device 120 (e.g., the receiving device) is associated with adifferent media service account corresponding to a different user.

At operation 1120, playback device 120 can present the media asset sentby media server 140. For example, media application 122 on playbackdevice 120 can present the audio and/or video data corresponding to themedia item requested at operation 1114.

While the implementations described with reference to process 1100 aboveuse a device identifier to tie the delegate token to a specific playbackdevice, process 1100 can be performed without tying the delegate tokento a specific device identifier. Thus, step 1102 may be optional and thefollowing steps can be performed to generate a delegate token withoutobtaining or using the device identifier for the playback device. Forexample, media service 142 can generate a delegate token without usingthe playback device identifier and validate the delegate token withoutverifying the playback device identifier in the delegate token.

In some implementations, delegate tokens can be archived with playbackqueues and/or media items. For example, a user may wish to re-play aplayback queue at a later time but may not be able to play a particularmedia item in the playback queue without a delegate token. Playbackdevice 120 can archive the playback queue and delegate tokens so thatthe media item in the playback queue can be played back later using thedelegate token.

To enable the reader to obtain a clear understanding of thetechnological concepts described herein, the above processes describespecific steps performed in a specific order. However, one or more ofthe steps of a particular process may be rearranged and/or omitted whileremaining within the contemplated scope of the technology disclosedherein. Moreover, different processes, and/or steps thereof, may becombined, recombined, rearranged, omitted, and/or executed in parallelto create different process flows that are also within the contemplatedscope of the technology disclosed herein. Additionally, while theprocesses above may omit or briefly summarize some of the details of thetechnologies disclosed herein for clarity, the details described in theparagraphs above may be combined with the process steps described aboveto get a more complete and comprehensive understanding of theseprocesses and the technologies disclosed herein.

Graphical User Interfaces

This disclosure above describes various Graphical User Interfaces (GUIs)for implementing various features, processes or workflows. These GUIscan be presented on a variety of electronic devices including but notlimited to laptop computers, desktop computers, computer terminals,television systems, tablet computers, e-book readers and smart phones.One or more of these electronic devices can include a touch-sensitivesurface. The touch-sensitive surface can process multiple simultaneouspoints of input, including processing data related to the pressure,degree or position of each point of input. Such processing canfacilitate gestures with multiple fingers, including pinching andswiping.

When the disclosure refers to “select” or “selecting” user interfaceelements in a GUI, these terms are understood to include clicking or“hovering” with a mouse or other input device over a user interfaceelement, or touching, tapping or gesturing with one or more fingers orstylus on a user interface element. User interface elements can bevirtual buttons, menus, selectors, switches, sliders, scrubbers, knobs,thumbnails, links, icons, radio buttons, checkboxes and any othermechanism for receiving input from, or providing feedback to a user.

Privacy

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Example System Architecture

FIG. 12 is a block diagram of an example computing device 1200 that canimplement the features and processes of FIGS. 1-11. The computing device1200 can include a memory interface 1202, one or more data processors,image processors and/or central processing units 1204, and a peripheralsinterface 1206. The memory interface 1202, the one or more processors1204 and/or the peripherals interface 1206 can be separate components orcan be integrated in one or more integrated circuits. The variouscomponents in the computing device 1200 can be coupled by one or morecommunication buses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 1206 to facilitate multiple functionalities. For example, amotion sensor 1210, a light sensor 1212, and a proximity sensor 1214 canbe coupled to the peripherals interface 1206 to facilitate orientation,lighting, and proximity functions. Other sensors 1216 can also beconnected to the peripherals interface 1206, such as a global navigationsatellite system (GNSS) (e.g., GPS receiver), a temperature sensor, abiometric sensor, magnetometer or other sensing device, to facilitaterelated functionalities.

A camera subsystem 1220 and an optical sensor 1222, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips. The camera subsystem 1220 and theoptical sensor 1222 can be used to collect images of a user to be usedduring authentication of a user, e.g., by performing facial recognitionanalysis.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 1224, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 1224 can depend on the communication network(s)over which the computing device 1200 is intended to operate. Forexample, the computing device 1200 can include communication subsystems1224 designed to operate over a GSM network, a GPRS network, an EDGEnetwork, a Wi-Fi or WiMax network, and a Bluetooth™ network. Inparticular, the wireless communication subsystems 1224 can includehosting protocols such that the device 100 can be configured as a basestation for other wireless devices.

An audio subsystem 1226 can be coupled to a speaker 1228 and amicrophone 1230 to facilitate voice-enabled functions, such as speakerrecognition, voice replication, digital recording, and telephonyfunctions. The audio subsystem 1226 can be configured to facilitateprocessing voice commands, voiceprinting and voice authentication, forexample.

The I/O subsystem 1240 can include a touch-surface controller 1242and/or other input controller(s) 1244. The touch-surface controller 1242can be coupled to a touch surface 1246. The touch surface 1246 andtouch-surface controller 1242 can, for example, detect contact andmovement or break thereof using any of a plurality of touch sensitivitytechnologies, including but not limited to capacitive, resistive,infrared, and surface acoustic wave technologies, as well as otherproximity sensor arrays or other elements for determining one or morepoints of contact with the touch surface 1246.

The other input controller(s) 1244 can be coupled to other input/controldevices 1248, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 1228 and/or the microphone 1230.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch surface 1246; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the computing device 1200 on or off. Pressing the button for athird duration can activate a voice control, or voice command, modulethat enables the user to speak commands into the microphone 1230 tocause the device to execute the spoken command. The user can customize afunctionality of one or more of the buttons. The touch surface 1246 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the computing device 1200 can present recordedaudio and/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the computing device 1200 can include the functionalityof an MP3 player, such as an iPod™. The computing device 1200 can,therefore, include a 36-pin connector that is compatible with the iPod.Other input/output and control devices can also be used.

The memory interface 1202 can be coupled to memory 1250. The memory 1250can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 1250can store an operating system 1252, such as Darwin, RTXC, LINUX, UNIX,OS X, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 1252 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 1252 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 1252 can includeinstructions for performing voice authentication. For example, operatingsystem 1252 can implement the playback queue transfer and credentialdelegation features as described with reference to FIGS. 1-11.

The memory 1250 can also store communication instructions 1254 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 1250 can includegraphical user interface instructions 1256 to facilitate graphic userinterface processing; sensor processing instructions 1258 to facilitatesensor-related processing and functions; phone instructions 1260 tofacilitate phone-related processes and functions; electronic messaginginstructions 1262 to facilitate electronic-messaging related processesand functions; web browsing instructions 1264 to facilitate webbrowsing-related processes and functions; media processing instructions1266 to facilitate media processing-related processes and functions;GNSS/Navigation instructions 1268 to facilitate GNSS andnavigation-related processes and instructions; and/or camerainstructions 1270 to facilitate camera-related processes and functions.

The memory 1250 can store other software instructions 1272 to facilitateother processes and functions, such as the playback queue transfer andcredential delegation processes and functions as described withreference to FIGS. 1-11.

The memory 1250 can also store other software instructions 1274, such asweb video instructions to facilitate web video-related processes andfunctions; and/or web shopping instructions to facilitate webshopping-related processes and functions. In some implementations, themedia processing instructions 1266 are divided into audio processinginstructions and video processing instructions to facilitate audioprocessing-related processes and functions and video processing-relatedprocesses and functions, respectively.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 1250 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the computing device 1200 can be implemented in hardwareand/or in software, including in one or more signal processing and/orapplication specific integrated circuits.

What is claimed is:
 1. A method comprising: receiving, by a firstcomputing device, a playback queue from a second computing device,wherein the playback queue includes one or more media items, and whereineach of the one or more media items comprises a media item identifier, afirst account identifier, and a delegate token; selecting, by the firstcomputing device, a media item from the one or more media items forplayback by the first computing device; determining, by the firstcomputing device, that the media item is associated with the firstaccount identifier that is distinct from a second account identifierconfigured for the first computing device, wherein the media item is notaccessible using the second account identifier configured on the firstcomputing device; sending, by the first computing device, a media assetrequest to a third computing device, the media asset request includingthe media item identifier, the first account identifier, the delegatetoken, and a device identifier for the first computing device;receiving, by the first computing device, a media asset corresponding tothe media item identifier responsive to the third computing devicevalidating the delegate token based on the first account identifier andthe device identifier; and presenting, by the first computing device,the media asset corresponding to the selected media item.
 2. The methodof claim 1, wherein the delegate token allows the first computing deviceassociated with the second account identifier to access the media itemthrough a media service account corresponding to the first accountidentifier.
 3. The method of claim 1, wherein the first accountidentifier identifies a user account used to enqueue the media item inthe playback queue.
 4. The method of claim 1, wherein the delegate tokencan only be used by the first computing device to access the media item.5. The method of claim 1, wherein the delegate token is generated by thethird computing device.
 6. The method of claim 1, wherein the delegatetoken is stored by the third computing device in association with thefirst account identifier and the device identifier of the firstcomputing device.
 7. The method of claim 1, wherein the media itemfurther comprises a time offset indicating a current position ofplayback for the media item responsive to the media item being selectedfor playback by the first computing device concurrent to the media itemplaying on the second computing device.
 8. The method of claim 1,further comprising: displaying, by the first computing device, a userinterface on a lock screen of the first computing device; and receiving,by the first computing device, user input selecting transfer of theplayback queue from the second computing device, wherein the playbackqueue is received from the second computing device responsive to userselection of transferring the playback queue.
 9. A non-transitorycomputer readable medium including one or more sequences of instructionsthat, when executed by one or more processors, cause the processors toperform operations comprising: receiving, by a first computing device, aplayback queue from a second computing device, wherein the playbackqueue includes one or more media items, and wherein each of the one ormore media items comprises a media item identifier, a first accountidentifier, and a delegate token; selecting, by the first computingdevice, a media item from the one or more media items for playback bythe first computing device; determining, by the first computing device,that the media item is associated with the first account identifier thatis distinct from a second account identifier configured for the firstcomputing device, wherein the media item is not accessible using thesecond account identifier configured on the first computing device;sending, by the first computing device, a media asset request to a thirdcomputing device, the media asset request including the media itemidentifier, the first account identifier, the delegate token, and adevice identifier for the first computing device; receiving, by thefirst computing device, a media asset corresponding to the media itemidentifier responsive to the third computing device validating thedelegate token based on the first account identifier and the deviceidentifier; and presenting, by the first computing device, the mediaasset corresponding to the selected media item.
 10. The non-transitorycomputer readable medium of claim 9, wherein the delegate token allowsthe first computing device associated with the second account identifierto access the media item through a media service account correspondingto the first account identifier.
 11. The non-transitory computerreadable medium of claim 9, wherein the first account identifieridentifies a user account used to enqueue the media item in the playbackqueue.
 12. The non-transitory computer readable medium of claim 9,wherein the delegate token can only be used by the first computingdevice to access the media item.
 13. The non-transitory computerreadable medium of claim 9, wherein the delegate token is generated bythe third computing device.
 14. The non-transitory computer readablemedium of claim 9, wherein the delegate token is stored by the thirdcomputing device in association with the first account identifier andthe device identifier of the first computing device.
 15. A systemcomprising: one or more processors; and a non-transitory computerreadable medium including one or more sequences of instructions that,when executed by one or more processors, cause the processors to performoperations comprising: receiving, by a first computing device, aplayback queue from a second computing device, wherein the playbackqueue includes one or more media items, and wherein each of the one ormore media items comprises a media item identifier, a first accountidentifier, and a delegate token; selecting, by the first computingdevice, a media item from the one or more media items for playback bythe first computing device; determining, by the first computing device,that the media item is associated with the first account identifier thatis distinct from a second account identifier configured for the firstcomputing device, wherein the media item is not accessible using thesecond account identifier configured on the first computing device;sending, by the first computing device, a media asset request to a thirdcomputing device, the media asset request including the media itemidentifier, the first account identifier, the delegate token, and adevice identifier for the first computing device; receiving, by thefirst computing device, a media asset corresponding to the media itemidentifier responsive to the third computing device validating thedelegate token based on the first account identifier and the deviceidentifier; and presenting, by the first computing device, the mediaasset corresponding to the selected media item.
 16. The system of claim15, wherein the delegate token allows the first computing deviceassociated with the second account identifier to access the media itemthrough a media service account corresponding to the first accountidentifier.
 17. The system of claim 15, wherein the first accountidentifier identifies a user account used to enqueue the media item inthe playback queue.
 18. The system of claim 15, wherein the delegatetoken can only be used by the first computing device to access the mediaitem.
 19. The system of claim 15, wherein the delegate token isgenerated by the third computing device.
 20. The system of claim 15,wherein the delegate token is stored by the third computing device inassociation with the first account identifier and the device identifierof the first computing device.